home *** CD-ROM | disk | FTP | other *** search
- Path: news.tau.ac.il!usenet
- From: Avi Lev <avil@sapiens.com>
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: 680X0 -> PPC translator?
- Date: Wed, 06 Mar 1996 08:55:04 +0200
- Organization: Sapiens Technologies
- Message-ID: <313D36C8.72B7@sapiens.com>
- References: <4fstt2$old@newsstand.cit.cornell.edu> <PETERM.96Feb19135541@tui.maths.irl.cri.nz> <4glch6$rle@ra.nrl.navy.mil> <1190.6631T892T581@und.ida.liu.se> <Ronald.07ii@noblehouse.xs4all.nl> <31355992.58CD@afrodite.kih.no>
- NNTP-Posting-Host: honda.sapiens.co.il
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0 (WinNT; I)
-
- Paul Kenneth Egell-johnsen wrote:
- >
- > Ronald van Eijck wrote:
- >
- > > How about an interpreter with a special 'memory mode' This means that you
- > > can start an application under the interpreter which then remembers the
- > > translated version of the code it interpreted. If you run the program once
- > > this way and make sure you have the largest part of the program executed at
- > > least once, especially those parts that need the speed, the interpreter can
- > > write out a new binary with the translated parts replaced. A system that
- > > would do this automatically and incrementally everytime you run the application
- > > would translate more and more of the program to native code everytime you
- > > run it. Still an awful complex piece of code I think but very nice once
- > > you have it. Goodbye to self modifying code but that should have been outlawed
- > > a long time ago anyway.
-
- Hi guys, you can argue whether it's possible or not as much as
- you want i claim IT'S DAMN POSSIBLE!!! it's just that no one is
- brave enough to take it on him/her-self to do it cuz the job is
- just too hard. assuming you have a completely compatible OS
- written in native PPC code, translation shoudn't be more
- difficult than translating mov cx,3 (in x86) to move a2,3 (in
- 680x0) so what's the problem?! finding out which parts are code
- and which ones are data is very easy for someone who's familiar
- with the executable file format of the Amiga, there're
- DATA_HUNK's and there're CODE_HUNK's isn't that enough to
- recognise what is what, just translate the CODE_HUNK's and
- you're done. the main concern is efficiency just as it is with
- normal source compilers, however PPC's are faster anyway so even
- the most inefficient translator will do the job quite nice in
- fact. self-modifying code isn't dead by the way it's very much
- alive'n kickin', hey it's the best defense against software
- crackers isn't it?!
- thanks for 'listening', Avi.
-